home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Diamond Collection
/
The Diamond Collection (Software Vault)(Digital Impact).ISO
/
cdr37
/
dnet106.zip
/
00000006.DAT
< prev
next >
Wrap
Text File
|
1995-04-12
|
14KB
|
273 lines
┌────── ┌─ ┌─ ┌────── ┌──────────
┌─ ┌─ ┌─┌─ ┌─ ┌─ ┌─
┌─ ┌─ ┌─ ┌─ ┌─ ┌──── ┌─
┌─ ┌─ ┌─ ┌─┌─ ┌─ ┌─
┌────── ┌─ ┌┌─ ┌────── ┌─
(Dynamic Network)
This file is required reading if you would like to become a:
Zone Coordinator (ZC) Regional Coordinator (RC), Net Coordinator (NC),
or Net Echo Coordinator (Hub) All of the above postitions are what could
be called 'management' postitions within dNet, as such, the persons holding
these titles must be familiar with dNet policy. Please read the entire
document (its not too long).
If something in this document is not covered, or is unclear, please submit
suggested changes to the Network Administrator via your Net Coordinator.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
1.0 - dNet TOPOLOGY
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Network Administrator
=====================
|
{Zone Coordinators}
_________________________|________________________
| | | | | |
N. America Europe Australia S. America Africa Asia
|
|
|
{Regional Coordinators}
_____|____________________________________________________________
| | | | | |
N.Eastern Eastern Central Mountain Pacific Sattelite
|
______________|_______________
NC| NC| NC|
|-------------|--------------|
NEC NEC NEC
|
____________|____________
| | | | |
Node Node Node Node Node
=============================================================================
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
1.0 ZONES
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Zone Coordinators will develope the geographic layouts for their respective
zone, however; all ZCs will adhere to standard dNet toplogy for developing
their zone.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
1.1 REGIONS
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
REGIONAL COORDINATORS ARE RESPONSIBLE FOR THE SMOOTH FLOW OF MESSAGE TRAFFIC
IN THE AREAS SET FORTH BELOW FOR ZONE 25. ALL OTHER REGIONS SHALL BE
DEVELOPED BY THE RESPECTIVE ZONE COORDINATOR.
----------------------------------------------------------------------------
N. East US - All areas in the eastern time zone North of and including VA.
Eastern US - All areas in the eastern time zone South of Virginia
Central US - All areas in the Central time zone.
Mountain US - All areas in the Mountain time zone.
Pacific US - All areas in the Pacific time zone.
Sattelite - The Sattelite Regional Coordinator is based in Jacksonville
Florida. SatLink will handle all Hubs that receive their mail
through the sattelite regardless of their geographical location.
If you have a sattelite link, and wish to receive dNet via
sattelite send your application for hub status to the
Sattelite Regional Coordinator.
* When you apply for Hub status, apply to the appropriate RC for the
time zone in which your system is located.
=============================================================================
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
2.0 - MAIL DISTRIBUTION
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
■ The Network Administrator is the focal point for all mail.
■ Each Zone Regional coordinator shall poll their Zone Coordinator for mail
at least once per day, or per other instructions set forth by the ZC.
■ Each Hub shall poll their repsective Regional Coordinator at least once
per day.
■ Each Node shall poll their repsective hubs according to the policy set
forth by the NEC (hub). (Preferably once per day)
=============================================================================
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
3.0 - STRUCTURE
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
dNet will rely on Zone Coordinators, Regional Coordinators and Hubs to
provide organization for the Network. RC's shall ensure that each net
within their Region conforms to the following structure.
Regional Coordinator: RC's oversee the Nets in their respective time zone.
[ RC ] Any application for a new Net shall be sent to the
appropriate RC for approval. RC's are the approval
authority for node applications. RC's submit requests
for node numbers to the Nodelist coordinator.
RC's are the final authority for all dNet activity
within their zone. Disputes with RC decisions may
be fowarded to the Network Administrator for final
disposition via the NC, however, unless their is
gross misjudement by the RC, the decision of the
Network Administrator will most likely favor the RC.
All RC's MUST have FTSC capable systems.
Net Coordinator : NC's shall be the Administrative Link between their
[ NC ] net, and region. Most often, during the early stages
of a Net, the Net Coordinator will also act as the
Net Echo Coordinator. Each application for dNet must
be submitted to Region via the NC. NC's will assure
that each application is complete before fowarding
to Region. NC's may grant temporary approval for
new nodes until final approval from the RC.
It is also the responsibility of the NC to assure
that there is an ACTIVE NEC for their Net. All NC's
MUST have FTSC capable systems.
Net Echo Coordinator: NEC's shall be the physical link between their Net
[ NEC ] and Region. NEC's are the systems that will transfer
mail to and from Region for their respective Net.
NEC's are also referred to as Hubs. NEC's MUST accept
routed Netmail from their nodes, outbound to other
segments of dNet. All NEC's MUST be able to provide
FTSC and QWK mail services.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
4.0 - REQUIREMENTS
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
The following are requirements to be met by all ZC's RC's, NC's, and NEC's.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
4.1 - REQUIREMENTS.GENERAL
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
i. Taglines
EVERY tagline in dNet must follow this format:
dNet : <Your BBS Name> : <Optional........> : <Your dNET Node #> if FTSC
<BBS Phone Number> if QWK
ii. Aliases
Aliases are allowed in the ADULT conference areas ONLY. Violations of
the policy on Aliases will be handled with extreme prejudice.
iii. Sig Lines
Signature Lines are to be NO MORE than two lines long. Violations of
the policy on sig lines will also be handled with extreme prejudice.
iv. Initial Posts
Every new NC, NEC, and RC is expected to announce their BBS in the
Admin echo when they are successfully turned on and transferring mail.
(Announcements are also encouraged in other echos)
v. Every system in dNet is strongly encouraged to _actively_ recruit new
nodes. Success in dNet is measured by growth, stability, and
efficient operation. Stability and efficieny are built in to the
structure of the net, growth is up to the members passing the word.
vi. Professionalism is required of each member. A sloppily handled
network is bound for failure. If you have a problem, use appropriate
channels to resolve the problem (NC, RC, ZC, Network Administrator).
In other words, please do not air dirty laundry in public forums.
vii. Each and every dNet SysOp is stongly urged to advertise the fact that
they carry dNet, and to post regularly in dNet conference areas.
Your users will not be interested if they see that you aren't.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
4.2 - REQUIREMENTS.SPECIFIC
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
i. Zone Coordinators, Regional Coordinators and Net Echo Coordinators:
- You must have a Front End Mailer and FTSC tossing capabilities.
- You must have complete knowledge on operation of the above software.
- Your system must process Areafix Requests Automatically.
- You must be willing and able to assist every Net/Node that desires
to setup under your region/net.
- You must run a full time Mailer. CA nodelist flags will not be used
on Zone/Region/NEC Node Numbers.
- You must be completely familiar with these rules.
- The following files must be FREQ'able from your system:
DNETxx.ZIP (Info Pack), DNET_NL (Current Nodelist)
- Net Echo Coordinators: You will assure that all local and state laws
have been complied with before the release of any adult materials
(files, messages) to node SysOps in your Net. You assume full
responsibility for actions arising out of failure to comply with this
requirement.
ii. Net Coordinators:
- You must have a Front End Mailer.
- You must run a full time Mailer. CA nodelist flags will not be used
on NC Node Numbers.
- You must be completely familiar with these rules.
- The following files must be FREQ'able from your system:
DNETxx.ZIP (Info Pack), DNET_NL (Current Nodelist)
- You must process node applications within 24hrs of receipt.
- You must make alternate arrangements to assure mail delivery and
pickup for your net, should your NEC go down (crash).
- You will maintain a hardcopy file of proof of age for all node
SysOps that receive adult echos. Copies of this file must be sent
upon request to your RC or the Network Administrator within 96 hours.
=============================================================================
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
5.0 - SUMMARY
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
In the likely event that a situation arises that has not been covered
by this document, the problem shall be handled at the lowest level.
Zone Coordinators are the BOSS for their respective zones.
Regional Coordinators are the BOSS for their respective regions.
The word of a ZC or RC is the word of the Network Administrator. Only in
rare cases of gross misjudgement will the decision of either be overturned
by the Network Administrator.
John Hopke is the Network Administrator and owner of dNet.
John Hopke shall remain the Network Administrator of dNet until such time
that he decides to resign, at which time he will appoint the successor to
the Network Administrator position.
The Network Administrator, Zone Coordinators, Regional Coordinators,
Net Coordinators and Net Echo Coordinators shall in no way be held liable
for any damages, emotional distress, lost revenues, damaged equipment,
broken contracts, or any other negative/costly situation that may arise
from the use of dNet or the information obtained through dNet or any
version of the dNet information pack.
In the event any of the above mentioned parties are found liable for
ANY damages or punitive awards not covered above, the damages/awards(s)
shall not exceed $1.00 (U.S Dollar), and the plaintiff agrees to cover
_all_ legal fees.
The Network administrator reserves the right to modify in whole or in part
any portion of this document. All dNet systems are bound to follow the
provisions of current policy as promulgated by the Network Administrator.
By applying for any status (Node, Hub, NC, RC, ZC) in dNet, you agree to
the policies set forth in the most current revsion of this document.
============================== <eof> ====================================